Fixes #3966

Internally, start & end dates are converted to exclusive range to accommodate the interval logic and are transformed back to inclusive during render / evaluation.

The issue is apparent during plan because:

• When running sqlmesh plan --start <date> --end <date>, we apply the missing interval logic and propagate the exclusive range to render_audit_query; We then create the BETWEEN filter manually without converting the range back to inclusive, as is the case in all other render calls

• When running sqlmesh audit --start <date> --end <date>, the dates are propagated as-is